Purpose

This pull request updates the infrastructure deployment scripts and templates to improve how the Azure AI Foundry resource is referenced and passed between modules and scripts. The main change is switching from using the AI Foundry name and resource group to using the full resource ID, which simplifies resource referencing and enhances reliability. Several parameters and outputs are renamed or replaced to support this approach.

Infrastructure Template and Output Refactoring:

• The Bicep and ARM templates now output the AI Foundry resource ID (aiFoundryId) instead of the name and resource group, and all downstream references are updated to consume this resource ID.

Script Parameter and Usage Updates:

• The shell scripts (process_sample_data.sh and run_create_index_scripts.sh) are updated to accept and use the AI Foundry resource ID (aif_resource_id) instead of separate name and resource group parameters, and usage instructions are updated accordingly.

Resource Definition Improvements:

• The Bicep deployment logic is enhanced to conditionally create or reference an existing AI Foundry resource, improving support for deployments that reuse existing Azure resources.

Other Minor Infrastructure Updates:

• The allowed regions parameter in main.bicep is reformatted for readability.
• Template hash values in the generated ARM templates are updated to reflect the changes.
  These changes streamline resource management by using resource IDs, reduce parameter complexity, and improve deployment flexibility and reliability.

Does this introduce a breaking change?

• Yes
• No

Golden Path Validation

• I have tested the primary workflows (the "golden path") to ensure they function correctly without errors.

Deployment Validation

• I have validated the deployment process successfully and all services are running as expected with this change.

What to Check

Verify that the following are valid

• ...

Other Information